running on a laptop disconnected from the network

Hi,

I have a need to be able to disconnect a laptop from the network and take it to the clients offices and use DOORS in their office.

When the database was stored on the laptop this was easy, borrow the licence from the server onto the laptop and away we go. However that meant no-one else could access the DOORS database while the laptop was off the network.

As we use DOORS more now we've put the database onto a server to make it more useable but this means we cant take a laptop off the network as it's still trying to look for the database on the network.

I can easily partition the modules needed at the clients but this doesnt help until I can get the laptop looking for a different database.

Any suggestions?

Thanks in advance
Neil
nmuncey - Thu Oct 29 22:07:22 EDT 2009

Re: running on a laptop disconnected from the network
SystemAdmin - Thu Oct 29 22:57:09 EDT 2009

Hi Neil,

I'm not sure how advanced your understanding is of how the DOORS client connects with a DOORS DB server, so please excuse me if the following is too detailed.

You need to install a local DOORS DB on your laptop and redirect the DOORS client on the laptop to connect with that local DB when you're off line. You can then restore a Partition copy or an Archive copy of the DOORS project data you that you wish to show the customer on this local DOORS DB. You will need to know the TCP address of the locally installed DOORS DB - this is in the format of <port>@<hostname> e.g. 36677@ComputerName

When a DOORS client is installed for the first time, it will have been configured with the TCP address of a specific target DOORS DB to connect with. This information is stored in the Windows registry. However, you can create a DOORS client shortcut that forces the client to connect with another DOORS DB and to ignore the registry settings. If you don't already have a DOORS client shortcut on your desktop, create one by doing a RH mouse click over the DOORS client icon in the Start menu, select copy, and then paste this onto the desktop. If a shortcut already exists on the desktop, make a copy of it on the desktop. Look at the properties of the copied shortcut (single click icon, RH mouse, select Properties) - under the "shortcut" tab of the Properties window you will see a field named "Target" with something like this in it:

"C:\Program Files\Telelogic\DOORS 9.1\bin\doors.exe"

There is a switch command you can add to the end of doors.exe so that when this shortcut is dble clicked to launch the DOORS client, the client will connect with a specified DOORS DB. The format of the switch command is as follows:

-data <port>@<hostname>

So modify the Target field so that it looks like the following - with the appropriate values for port and hostname entered:

"C:\Program Files\Telelogic\DOORS 9.1\bin\doors.exe" -data <port>@<hostname>

Rename the DOORS client shortcut so that you know that this shortcut will connect to the local DOORS DB on your laptop. Dble click on the short-cut, it should now connect the DOORS client to the local DB.


Paul Miller

Re: running on a laptop disconnected from the network
sammyc - Fri Oct 30 08:13:43 EDT 2009

If you are using DOORS 9.2, consider the RIF exchange that is simpler to create and synch up changes btw 2 databases.

Re: running on a laptop disconnected from the network
nmuncey - Sun Nov 01 14:58:03 EST 2009

SystemAdmin - Thu Oct 29 22:57:09 EDT 2009
Hi Neil,

I'm not sure how advanced your understanding is of how the DOORS client connects with a DOORS DB server, so please excuse me if the following is too detailed.

You need to install a local DOORS DB on your laptop and redirect the DOORS client on the laptop to connect with that local DB when you're off line. You can then restore a Partition copy or an Archive copy of the DOORS project data you that you wish to show the customer on this local DOORS DB. You will need to know the TCP address of the locally installed DOORS DB - this is in the format of <port>@<hostname> e.g. 36677@ComputerName

When a DOORS client is installed for the first time, it will have been configured with the TCP address of a specific target DOORS DB to connect with. This information is stored in the Windows registry. However, you can create a DOORS client shortcut that forces the client to connect with another DOORS DB and to ignore the registry settings. If you don't already have a DOORS client shortcut on your desktop, create one by doing a RH mouse click over the DOORS client icon in the Start menu, select copy, and then paste this onto the desktop. If a shortcut already exists on the desktop, make a copy of it on the desktop. Look at the properties of the copied shortcut (single click icon, RH mouse, select Properties) - under the "shortcut" tab of the Properties window you will see a field named "Target" with something like this in it:

"C:\Program Files\Telelogic\DOORS 9.1\bin\doors.exe"

There is a switch command you can add to the end of doors.exe so that when this shortcut is dble clicked to launch the DOORS client, the client will connect with a specified DOORS DB. The format of the switch command is as follows:

-data <port>@<hostname>

So modify the Target field so that it looks like the following - with the appropriate values for port and hostname entered:

"C:\Program Files\Telelogic\DOORS 9.1\bin\doors.exe" -data <port>@<hostname>

Rename the DOORS client shortcut so that you know that this shortcut will connect to the local DOORS DB on your laptop. Dble click on the short-cut, it should now connect the DOORS client to the local DB.


Paul Miller

Paul,

Many thanks for that. It's exactly what I was after. I had figured out the two databases bit and your info about the command line switch is enought for me to get it all up and runnning.

Thanks for your help.

Neil